@masiulis anything actionable here? Really want to get this merged, happy to create a new fix if you don't think this will address #141

Hey @ryanoillataguerre @Yo1L @h-bragg, sorry guys, I got a bit delayed with work stuff. I need to investigate this topic more, because the code here works in some cases (probably the most common ones) but it works differently from how columns are matched. This PR checks if labels match exactly, while columns match nearby values too with levenshtein distance. On the other hand, adding levenshtein logic here could make column matching exponentially slower.

I will try to implement what I suggested in this comment. If it's too slow I might add this PR as the default and allow enabling levenshtein as an optional flag.

EDIT: decided to implement simple check if imported value matches value / label of any field options. No levenshtein distance for now as it would be too slow on large data sets.

Released in 4.4.0 - you will need to set autoMapSelectValues={true} - this flag will be set to true by default in the next major release, but I wanted to release it as a non-breaking change.

thank you @masiulis it works like a charm! Great job